Skip to content

Conversation

@chickenchickenlove
Copy link
Contributor

Currently, some test codes create KafkaBroker by calling new EmbeddedKafkaBroker(...).

Using the @EmbeddedKafka annotation to create a broker can help minimize the amount of code that needs to be modified when major updates(579ae6a), such as the changes to the broker implementation in Spring for Apache Kafka 4.0.0, occur.

From this perspective, I believe that using @EmbeddedKafka offers a slight improvement in terms of maintainability for test code.

When you have time, Please take a look. 🙇‍♂️

Copy link
Member

@artembilan artembilan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't this a reason to do this refactoring since having an embedded Kafka as a bean is totally valid scenario. Therefore we have to have some tests in the project to cover that behavior.

What I meant on your other PR that there is no reason to go extra mile if we can just use respective annotation.

Does that make sense?

@chickenchickenlove
Copy link
Contributor Author

@artembilan thanks for your time!
It makes sense!
I'm going to close this PR 🙇‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants